🚅 Deployed to the rivet-pr-4492 environment in rivet-frontend

Service	Status	Web	Updated (UTC)
kitchen-sink	❌ Build Failed (View Logs)	Web	Mar 24, 2026 at 11:31 am
website	❌ Build Failed (View Logs)	Web	Mar 24, 2026 at 3:29 am
frontend-inspector	❌ Build Failed (View Logs)	Web	Mar 24, 2026 at 3:29 am
frontend-cloud	❌ Build Failed (View Logs)	Web	Mar 24, 2026 at 3:29 am
mcp-hub	✅ Success (View Logs)	Web	Mar 24, 2026 at 3:29 am
ladle	❌ Build Failed (View Logs)	Web	Mar 24, 2026 at 3:29 am

• fix(rivetkit): setup database before lifecycle hooks for c.db availability #4494
• fix(rivetkit): remove drizzle-orm peer dep and add runtime version check #4492 👈 (View in Graphite)
• chore(skill): add version check to rivetkit skill #4491
• fix(rivetkit): prevent Turbopack from tracing sqlite-vfs dynamic import #4490
• fix(rivetkit): warn when manager port falls back to a different port #4489
• fix(rivetkit): clear connectableTs on actor sleep #4488
• fix(rivetkit): gate node:sqlite behind RIVETKIT_NODE_SQLITE env var #4487
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

PR Review: fix(rivetkit): remove drizzle-orm peer dep and add runtime version check\n\nOverall this is a clean, well-scoped change. The runtime version check is a solid approach for optional feature dependencies. A few issues worth addressing.\n\n### Bug: Script exits 0 even when tests fail\n\ntest-drizzle-compat.sh uses set -euo pipefail but captures test failures with if/else, so those failures do not propagate. The script will exit 0 even if every version fails, making it useless in CI.\n\nAdd a final exit code check after the results summary.\n\n### Doc mismatch in CLAUDE.md\n\nThe new doc section says to update SUPPORTED_DRIZZLE_RANGE in mod.ts, but the actual constants are DRIZZLE_MIN and DRIZZLE_MAX. Should read: Update the DEFAULT_VERSIONS array in the script and DRIZZLE_MIN/DRIZZLE_MAX in src/db/drizzle/mod.ts when adding support for new drizzle releases.\n\n### Silent catch in checkDrizzleVersion could confuse future readers\n\nThe catch block silently swallows errors. If drizzle-orm is not installed, the require call will throw, but the real crash happens earlier at the ESM import level anyway. A comment would prevent this from looking like a silent failure bug.\n\n### Minor: Two-part version strings in isSupported\n\nDEFAULT_VERSIONS passes minor-only strings like 0.44 to pnpm add. If those ever reach isSupported, the split produces no patch segment. compareVersions handles this correctly via the ?? 0 fallback, treating it as 0.44.0. Worth a brief comment confirming this is intentional.\n\n### Nit: Script cleanup fallback\n\nThe pnpm install fallback in the cleanup trap (without --frozen-lockfile) could silently update the lockfile if the frozen install fails. Consider logging a warning rather than silently falling back to a mutable install.\n\n---\n\nGood change overall. The lazy check with drizzleVersionChecked, the createRequire pattern for ESM-safe JSON reads, and the backup/restore isolation in the test script are all solid choices.